home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950726-19950929
/
000222_news@columbia.edu_Thu Aug 24 14:36:26 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-12-25
|
5KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA22100
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Fri, 25 Aug 1995 02:36:44 -0400
Received: by apakabar.cc.columbia.edu id AA21577
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Fri, 25 Aug 1995 02:36:41 -0400
Path: news.columbia.edu!sol.ctr.columbia.edu!howland.reston.ans.net!newsfeed.internetmci.com!us.oracle.com!news.caldera.com!news.cc.utah.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit + TCP/IP
Message-Id: <1995Aug24.203626.59666@cc.usu.edu>
Date: 24 Aug 95 20:36:26 MDT
References: <41encq$1pl@raffles.technet.sg>
Organization: Utah State University
Lines: 105
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <41encq$1pl@raffles.technet.sg>, onglc@technet.sg (Robert Ong) writes:
> Hi,
>
> Thanks to all who replied to my earlier message regarding connecting
> PCs to a Vax computer via TCP/IP.
>
> One of your suppliers is supplying us a NE2000 compatible NIC. Apparently
> we are unable to connect the PC to the Vax when using this card. The error
> message we get is:
>
> Cannot access IP type packets
> Unable to initialise TCP/IP system, quitting.
> ?Cannot start the connection.
>
> When we replaced the card with the 3COM Etherlink II/TPs, no problem.
> The NET.CFG looks something like this:
Your NET.CFG file looks ok to me. However, in case no one has
pointed out a soft spot let me indicate that IRQ 3 is used by COM2 and
hence cannot coexist with the network board. Please check for hardware
conflicts.
In addition, not all NE-2000 clones are created equal, and as they
say, some are more equal than others.
The overall point is the lan driver may not load properly because
of hardware conflicts or the board does not match the driver. In such
cases Kermit (and IPXODI for that matter) will be unable to find a board
and declare errors such as you cite. Hints on loading are often displayed
as the MLID (board driver) is loading; they can be redirected to a log
file by > filename appended to the loading command. Here is an example
of what I mean:
@echo off
set nwlanguage=ENGLISH
c:\qemm\loadhi /r:2 c:\nwclient\lsl.com >startup.log
c:\qemm\loadhi /r:2 c:\nwclient\ne3200.com >>startup.log
c:\qemm\loadhi /r:2 c:\nwclient\ipxodi /d >>startup.log
c:\nwclient\vlm /mX /v4 /c=c:\nwclient\net.cfg >>startup.log
@echo on
Further, the MLID itself can report on its state by reinvoking
it with a /S argument, such as ne3200 /s shown below:
Novell NE3200 Ethernet MLID v2.04 (950405)
(C) Copyright 1991 - 1995 Novell, Inc. All Rights Reserved.
The following LAN drivers are loaded in memory:
Novell NE3200 Ethernet v2.04 is loaded at Segment D7F9h.
Slot 6, IRQ 5, Port 6000, Node Address 1B16A7D4 L
Max Frame 1514 bytes, Line Speed 10 Mbps, Bus ID 2
Board 1, Frame ETHERNET_II, LSB Mode
Board 2, Frame ETHERNET_802.3, LSB Mode
Board 3, Frame ETHERNET_802.2, LSB Mode
Board 4, Frame ETHERNET_SNAP, LSB Mode
(I have four frame kinds loaded for experimental purposes; only one,
Ethernet_II, is needed and recommended for general use.) Reinvokation
this way does not install a second instance of the driver, so this is
a safe test.
Finally, if you have another TCP/IP stack operating over the
same board then the same error message will be produced. The rule is
only one protocol stack of the same kind over one board.
Joe D.
> Link Support
> Buffers 8 1500
> MemPool 4096
> Max Boards 4
> Max Stacks 4
>
> Link Driver 3c503
> Port 300
> INT 5
> FRAME ETHERNET_II
> FRAME ETHERNET_802.2
> PROTOCOL IPX E0 ETHERNET_802.2
> PROTOCOL IP 800 ETHERNET_II
> PROTOCOL ARP 806 ETHERNET_II
> PROTOCOL RARP 8035 ETHERNET_II
>
> Link Driver NE2000
> Port 300
> INT 3
> FRAME ETHERNET_II
> FRAME ETHERNET_802.2
> PROTOCOL IPX 8137 ETHERNET_II
> PROTOCOL IP 800 ETHERNET_II
> PROTOCOL ARP 806 ETHERNET_II
> PROTOCOL RARP 8035 ETHERNET_II
>
> Netware DOS Requester
> Preferred Server="HQFS1"
> Name Context=".CSD.SMRT"
> First Network Drive=F
> Netware Protocol=NDS BIND
>
> Thanks in advance.
>
> Robert
> --
> +----------------------------------------------------------------+
> | Robert Ong Systems Analyst |
> | Computer Services Department onglc@technet.sg |
> | Singapore MRT Ltd (065)-331-1347 |
> +----------------------------------------------------------------+